-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PM-12400] Add private key regeneration SDK methods #1133
Conversation
remaining: UUID
I really shouldn't need to be fixing this
…tion' into km/pm-12400/private-key-regen
No New Or Fixed Issues Found |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1133 +/- ##
==========================================
+ Coverage 58.17% 58.54% +0.37%
==========================================
Files 197 197
Lines 13587 13745 +158
==========================================
+ Hits 7904 8047 +143
- Misses 5683 5698 +15 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, nice work!
@Thomas-Avery This will need to be moved to https://github.com/bitwarden/sdk-internal. It should be as simple as changing remote and pushing the branch. All the history is preserved in the new repo. |
Closing, opened on sdk-internal here bitwarden/sdk-internal#6 |
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-12400
📔 Objective
Add shared methods to enable private key regeneration in clients.
⏰ Reminders before review
team
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmedissue and could potentially benefit from discussion
:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes